home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Diamond Collection
/
The Diamond Collection (Software Vault)(Digital Impact).ISO
/
cdr37
/
tictr128.zip
/
READ.ME
< prev
next >
Wrap
Text File
|
1995-04-01
|
15KB
|
366 lines
TICTOSS BETA READ.ME
This version of TicToss is a BETA version under development for those systems
wishing to forward TIC files along to others (ie "hub support"). The support
is not yet complete, but has reached a milestone in development where we are
seeking input on our progress as well as validation of the integrity of the
software by others in the event we overlooked something. This release should
NOT be run unattended as it may experience difficulties and not be able to
recover. This release should NOT be placed online in a production environment
until you have VALIDATED everything as being in working order -- be kind to
those who pickup TICs from you as well as yourself.
Remember...this is a BETA, not a WIDE BETA...PLEASE protect your data!!!
UPGRADING TO THE BETA
We have included a copy of our sample distribution TICTOSS.CFG from the v1.10
release in this archive, but if you are not currently running this version
(or the most recent release version, which is v1.15) we encourage you to obtain
the complete package which includes complete documentation.
In order to upgrade there are a few new keywords for the configuration:
------------------------------------v1.20-------------------------------------
Initial beta release to interested parties -- be careful!
Address -- the Fidonet technology address to place in the TIC files; this
should be in the form Zone:Network/Node.Point
TicDir -- the directory where TIC files should be placed for others; this
is not the directory for incoming TIC files, but outgoing ones; also the
directory where we store our file for keeping track of the filename to use
for the TICs (SERIAL.NUM); in general you should peek at this directory,
but NOT modify any files;
NetMailDir -- the directory where the file attach should be written; at this
time only *.MSG file attaches are possible and there should not be any chance
for greater than 999 files in the directory at a time; which is almost
impossible under DOS, very workable under OS/2
SendTo -- instructs TicToss to send this area to someone else; the address for
the downlink should be in the same form as the Address keyword (see above),
followed by the downlink's password; this keyword should follow the Password
keyword in your configuration for the area you would like to send; there are
no limitations in the number of SendTo keywords you may have, repeat as often
as you need to do so just as you do with the AreaName keyword
------------------------------------v1.20------------------------------------
------------------------------------v1.21------------------------------------
Corrected problem with duplicate TIC files being created.
------------------------------------v1.21------------------------------------
------------------------------------v1.22------------------------------------
Corrected problem with undefined file echos causing abnormal termination
Added BinkleyTerm support; Preliminary and will need to be reworked before our
production release
Added Passthru support; also includes a PASSTHRU utility to check the PassThru
files to delete files after there are no additional TIC files
Added support for FD's KFS (Kill File Sent) flag so FD should now delete
the TIC files after sending them; TIC files created with v1.20 did not have
the KFS flag set so the TICs are still in your TicDir -- you may wish to
manually delete these IF you are sure the remote systems picked up the TICs
already (Assuming you are actually running TicToss online in some limited
fashion).
Released beta version of PassThru utility for purging PassThru files after the
files have been picked up; More info below
New Keywords:
FileAttach -- instructs TicToss whether to use *.MSG file attaches (as v1.20
did) or to write to BinkleyTerm's file attaches (.FLO files). Values possible
are MSG and FLO, default is MSG just in case you are NOT reading this. 8-)
FD users: FileAttach MSG
BT users: FileAttach FLO
Outbound -- FOR BINKLEYTERM USERS ONLY; if setting FileAttach to FLO, then
TicToss needs to know what directory is your default outbound. This is the
same value as the Hold keyword in your BINKLEY.CFG. Currently supported are
multiple Zones for those wishing to forward to distant Zones, as well as
points. The point support is limited to your own points -- ie if your address
is 1:136/1, you cannot forward files to 1:136/2.1. The point support uses the
point directory support that BinkleyTerm offers, but does not support the
"FakeNet". Probably best to wait until the BinkleyTerm support is further
enhanced before forwarding to points, but it is there if you need it.
PassThru -- Instructs TicToss to purge files AFTER all the downlink systems
have picked up their files; Similar to the DeleteArea keyword in that it is
used on areas individually and should be placed somewhere BEFORE the Password
line. PassThru files are stored in the directory with the TICs, this is
set using the TicDir keyword (above). All the normal keywords associated with
a non-PassThru area need to be declared -- a future release will make them
optional.
-------------------------------------v1.22---------------------------------
-------------------------------------v1.23---------------------------------
Corrected problem with TICs with long descriptions introduced prior to first
publicly available beta.
-------------------------------------v1.23---------------------------------
-------------------------------------v1.24---------------------------------
Several keywords used to configure TicToss were changed to more meaningful
names (hopefully)
TICTOSS.LOG formatted so it is more meaningful/readable;
Unknown keywords reported locally; some editors are embedding spaces in the
TICTOSS.CFG, usually when cut/paste operations are performed;
Added LOTS of error-checking/trapping as we prepare for a general release
Released "bare-bones" TicMake utility for creating TIC files; more info below
Eliminated the number of TIC files TicToss can handle in its InboundDir from
999 to UNLIMITED.
Expanded the number of *.MSG files TicToss can handle to 9999, up from 999
just in case. This only affects FD users who have FileAttach setup for MSG,
BinkleyTerm users setup for FLO don't have any limitation with file attaches.
Correct file sharing problem, discovered under OS/2
New/Modified Keywords:
Rename Inbound keyword to InboundDir.
Rename Outbound keyword to OutboundDir (BinkleyTerm users only).
TicMakePassword -- Password TicMake utility will use; TicToss will run okay
without this password defined if you are not using TicMake. Nice idea to
define it now.
-------------------------------------v1.24---------------------------------
-------------------------------------v1.25---------------------------------
Corrected an error-checking problem with the Address keyword
Corrected an error-checking problem with TIC keyword handling
Unless there are problem reports this will be the last beta version! Plans
are being made to migrate to our professional development tool to allow us
to move towards OS/2 and network ready version of TicToss -- we have run into
memory difficulties with out current development platform which have caused
many problems (it takes software to create software).
TicMgr is still not finished yet, but it will be released in beta form just
as soon as possible. We had hoped to ship an initial version by the end of
January, but this will slip into early to mid February due to a busy month
of January. FYI, TicMgr will allow your downlinks to add/delete file echos
"automatically" by sending netmail.
BTW, be sure to look at the enclosed SUPPORT.TXT for information on reaching
us to report any difficulties or suggestions.
-------------------------------------v1.25---------------------------------
-------------------------------------v1.26---------------------------------
Corrected an error dealing with writing *.MSG netmail file attaches.
Corrected condition where the PassThru database was not indexed correctly
when first initialized. PassThru utility will now rebuild the indexes from
the PassThru database -- Just run PassThru and it will clean up behind TicToss
v1.25 if needed automatically.
-------------------------------------v1.26---------------------------------
-------------------------------------v1.27---------------------------------
Several persons using the *.MSG support reported difficulty in sending files
to points. Due to those fields being labeled "optional" in the specification
apparently several developers did not implement the support. Please test the
point support if you are able to do so and drop a note to let me know if we
took care of the problem.
Corrected an EMM386 problem resulting the belief that all descriptions of files
wouldh have some delimiting character (space, comma, semicolon, etc).
-------------------------------------v1.27---------------------------------
-------------------------------------v1.28---------------------------------
Updated for the release of TicMgr v0.20, an automated way of maintaining file
echos for those who pickup TIC files from your system. TicMgr is being
distributed separately as it works with all versions of TicToss.
-------------------------------------v1.28---------------------------------
PassThru Utility Info:
Included in this archive is our PassThru utility. PASSTHRU.EXE should be
placed in the same directory as TICTOSS.CFG so it can read the path to the
TicDir (where TIC files and PassThru archives are stored). PassThru will
search to see if there are any archives (ZIP files, ARJ files, etc) which
are missing their TIC files. If there are multiple TICs for an archive,
PassThru should delete the record in its Passthru database (TicToss creates
and adds records for PassThru nodes). When the last TIC file is missing,
PassThru should erase the archive. If you are short on disk space, or have
a lot of persons picking up files as PassThru, you may wish to run PassThru
periodically during the day -- Be sure no one is online transferring files
or PassThru could erase a file before they download the archive.
TicMake Utility Info:
Included in this archive is a primitive TicMake utility. TICMAKE.EXE should
be placed in the same directory as TICTOSS.CFG so it can read various pieces
of information. Why primitive? It is EXTREMELY dependent on the TICTOSS.CFG
being formatted so that the FilePath is just under the AreaName. I would
prefer to have TicMake not read TICTOSS.CFG for the AreaName info, and would
also like to try to refrain from having a version of TicMake specific to each
version of TicToss. At this point I can only say it is more user-friendly
than HATCH <grin>, but very functional. TicMake will place the TIC it creates
in the InboundDir. TicToss should be run after TicMake and it will take care
of adding the description to the BBS file listing, and forwarding to others
(if the AreaName is one you are hubing). BTW, descriptions limited to 100
characters.
------------------------------------FD example-----------------------------
Mini-Example of New Keywords for FD users; FIDONEWS is a passthru file echo,
meaning that once everyone has picked up their files our PASSTHRU utility
will remove the files from your hard disk. NODEDIFF is NOT a passthru area.
Address 1:136/1
InboundDir c:\fd\file
TicDir c:\tictoss\ticdir
NetMailDir c:\binkley\netmail
FileAttach MSG
...[other configuration info omitted]...
AreaName FIDONEWS
Passthru
FilePath c:\Filebone\Fidonews
Dir c:\Filebone\Fidonews\Feather.Bbs
Host 1:136/2
Password guess
SendTo 1:136/5 beeper
AreaName NODEDIFF
FilePath c:\FileBone\NodeDiff
Dir c:\FileBone\NodeDiff\Feather.Bbs
Host 1:136/2
Password guess
SendTo 1:136/5 beeper
SendTo 1:136/4 cellular
-------------------------------------------------------------------------------
------------------------------Binkley Example----------------------------------
Mini-Example of New Keywords for BT users; FIDONEWS is a passthru file echo,
meaning that once everyone has picked up their files our PASSTHRU utility
will remove the files from your hard disk. NODEDIFF is NOT a passthru area.
Address 1:136/1
InboundDir c:\binkley\inbound
TicDir c:\tictoss\ticdir
NetMailDir c:\binkley\netmail
FileAttach FLO
OutboundDir c:\binkley\outbound
...[other configuration info omitted]...
AreaName FIDONEWS
Passthru
FilePath c:\Filebone\Fidonews
Dir c:\Filebone\Fidonews\Feather.Bbs
Host 1:136/2
Password guess
SendTo 1:136/5 beeper
AreaName NODEDIFF
FilePath c:\FileBone\NodeDiff
Dir c:\FileBone\NodeDiff\Feather.Bbs
Host 1:136/2
Password guess
SendTo 1:136/5 beeper
SendTo 1:136/4 cellular
--------------------------------------------------------------------------------
ACTIVELY PARTICIPATING IN THE BETA CYCLE
Below is a recent call for beta team members...if you would like to actively
participate then fill out and email.
-----
Call for TicToss Beta Team Members
December 3, 1994
TicToss, a Fidonet .TIC processor for FeatherNet Pro, RBBS, Spitfire, and
TriBBS, will enter into a public beta test in the near furture. The purpose of
the beta is to collect feedback from the TicToss community as we move towards
the completion of support for those TicToss systems wishing to forward files
to others ("hubbing"). While the beta test is intended for registered TicToss
users, anyone may participate if they have the time and inclination. The first
beta code should be delivered to the TicToss Beta Team around the 15th of Dec.
Distribution of TicToss betas will be made exclusively from our Support BBS
into the TicToss File Distribution Network (Fidonet FileBone). For those who
may not enjoy a connection to the FileBone, betas may be picked up via Fidonet
technology from the Support BBS. For our friends outside of North America,
remember the ftp.fidonet.org site which is supposed to carry the TicToss FDN
for anonymous ftping.
Beta test notes/feedback will be posted to the TicToss echo, which is available
only from our Support BBS at the present time at 28.8 v.fc or 19.2k ZyXEL.
Eddie Rowe
WER Development
Fidonet#1:136/1.0 (Support BBS)
318-325-6608 (Support BBS)
WerDev@Aol.Com
[Please import the TicToss.App into an email note rather than file attaching]
------------------------------------------------------------------------------
First & Last Name: _______________________________________
Fidonet Address: _________________________________________
Password: ________________________________________________
BBS & Version: _____________________________ Nodes: ____
Operating System: __________________________
Operating Environment: _____________________
Fidonet Mailer & Version: ________________________________
Method for obtaining betas: [ ] FileBone
[ ] Support BBS (via .TIC)